Upgrade Guide: Version 8.0.24

note

It is crucial to have Motadata AIOps baseline version of 8.0.23 to upgrade to Motadata AIOps version 8.0.24.

note

Ensure the PostgreSQL Database management system is installed.

Latest Motadata AIOps Installation Links

Motadata AIOps	Link
Ubuntu 24.04 (.iso)	Download
Ubuntu 24.04 (.ova)	Download
RHEL 9.4 (.tar)	Download

MotaAgent Installation Links

Operating System	Version	Link
Ubuntu	18, 20, 22, 24	Download
RHEL & CentOS	7, 8, 9	Download
Windows	Client OS 8 or Server OS 2012	Download
Windows	Client OS 10, 11 or Server OS 2016, 2019, 2022	Download
IBM-AIX	7.x	Download
SUSE Linux	15.6	Download

Upgrade Patches for 8.0.24

Operating System	Link
Ubuntu/RHEL	Download

Motadata Agent Manager Upgrade for 8.0.24

Operating System	Version	Link
Ubuntu/RHEL/Windows	All	Download

Agent Upgrade Patches for 8.0.24

Operating System	Version	Link
Ubuntu	18	Download
Ubuntu	20	Download
Ubuntu	22	Download
Ubuntu	24	Download
RHEL	7, 8, 9	Download
Windows	Client OS 8 or Server OS 2012	Download
Windows	Client OS 10, 11 or Server OS 2016, 2019, 2022	Download

Prerequisites for upgrading DB serverEnsure the Motadata AIOps service is not running before you perform this step.

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.
2. Contact Motadata: If the AIOPS version is 8.0.4 or below, please contact the Engineering team for assistance with the upgrade.
3. Free Disk Space: Ensure at least 60% free disk space on the /motadata partition to perform the patch. (Very Important)
4. Disk IOPS Verification: Verify that the disk IOPS are greater than 250 Mbps before starting the server using the following command:

   sudo dd if=/dev/mapper/vg0-motadata of=test1.img bs=1G count=1 oflag=dsync

Upgrade Steps

The upgrade steps varies for each deployment type. Please view the steps for your respective deployment architecture mentioned below.

Standalone Deployment

note

Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata Services: Stop the motadata services for the Observer server, Primary server, Secondary server, Database server, and Collectors.

   service motadata stop

3. Download AIOPS_UPGRADE.zip: Download and place the AIOPS_UPGRADE.zip file in the /motadata directory on all servers.

4. Unzip the Upgrade Patch:

   unzip AIOPS_UPGRADE.zip

5. Run the Upgrade Script: After unzipping the patch, run the upgrade script:

   sudo ./aiops-upgrade.sh
   note

   If the application and database are on the same server, proceed directly to Step 7. Otherwise, follow Step 6 first, and then move on to Step 7.

6. Master App Server Patch:

   • Start the motadata service for the master application server.
   • Wait for the patch to be applied.
   • Verify the patch application by checking the patch-related logs.
   • Ensure the GUI screen for the master server is accessible.

7. Final Steps:

   • Start the motadata service for the database server.
   • Start the motadata service for each collector, one by one.
   • Verify that data is visible on the monitoring screen.

HA Deployment

Pre-Upgrade Validation

note

Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.

note

Ensure there is no data sync backlog among Primary server, Secondary server, and Collector before proceeding to upgrade. Any data yet to be synced will be lost and cannot be recovered.

note

Ensure all servers are up and running. Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended.

Applying Upgrade Patch

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata Services on select servers: Except Primary App and Observer server, stop Motadata services on all other servers.

   sudo service motadata stop

3. Stop Motadata Services on Primary server: Once Motadata services has been stopped on all other servers, stop the service on the Primary server.

   sudo service motadata stop

4. Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.

   sudo service motadata-observer stop

5. Rename the Events folder at Observer Server: You will need to rename the events folder for Observer Server.

   sudo mv /motadata/motadata/events /motadata/motadata/events_old

6. Remove the ha-config* folders at App servers: You will need to rename the ha-config* folders for all App servers. (Primary App and Secondary App).

   sudo rm -rf /motadata/motadata/events/ha-config*

7. Perform a backup of Configuration files for all App servers: Ensure you create a backup for configuration files on all the App server (Primary App and Secondary App).

   sudo cp -r /motadata/motadata/config/ /tmp/ 

8. Remove JSON files from the temporary folder located in the Primary App server:

   sudo rm /tmp/config/*json 

9. Create a tar file in the Primary App server:

   sudo tar -cvf /tmp/config.tar /tmp/config/ 

10. Replicate the Config folder with non-JSON files from Primary App server to other App servers: You will need to copy the config folder containing non-JSON files to Secondary App server.

    sudo scp -r /tmp/config.tar motadata@<App_server_IP>:/tmp/ 

note

Kindly replace the <App_server_IP> placeholder with actual IP address of your App servers.

11. Overwrite the non-JSON files on other App servers: Execute the below-mentioned commands one by one on all other app servers Secondary App server.

    sudo tar -xvf /tmp/config.tar 

    sudo cp /tmp/tmp/config/* /motadata/motadata/config 
12. Perform the Upgrade on all Servers: You can now start upgrading all servers (Observer, Primary App. Primary DB, Secondary App, Secondary DB, and Collectors)

• Download AIOPS_UPGRADE.zip: Download and place the AIOPS_UPGRADE.zip file in the /motadata directory on all servers.

• Unzip the Upgrade Patch:

  unzip AIOPS_UPGRADE.zip

• Run the Upgrade Script: After unzipping the patch, run the upgrade script:

  sudo ./aiops-upgrade.sh

Migration Patch on Primary Server

13. Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.

    sudo service motadata-observer start

14. Start Motadata services on Primary server: Once Motadata services has been started on Observer server. Start the Motadata services on Primary App server.

    sudo service motadata start
    

15. Ensure Motadata service has started on Primary App server: Wait to ensure motadata services has been properly started on Primary App server.

    sudo watch service motadata status
    note

    Kindly wait for the motadata-metric-agent-service to spawn before proceeding to next step.

16. Stop Motadata service on Primary App server:

    sudo service motadata stop

17. Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.

    sudo service motadata-observer stop 

18. Remove the Events folder at Observer server: You will need to rename the events folder for Observer.

    sudo rm -rf /motadata/motadata/events 

19. Remove the ha-config* folders at Primary App server: You will need to remove the ha-config* folders for Primary App servers.

    sudo rm -rf /motadata/motadata/events/ha-config* 

Migration Patch on Secondary Server

20. Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.

    sudo service motadata-observer start 

21. Change the Secondary App server installation.mode to Primary: Change the installation.mode to primary from Secondary App server.

    note

    Kindly replace the <Primary/Secondary_App_server_IP> placeholder with actual IP address of your App servers. vi /motadata/motadata/config/motadata.json Change the given below entries, "installation.mode" : "PRIMARY", "event.publisher.host" : "<Secondary_App_server_IP>", "event.subscriber.host" : "<Secondary_App_server_IP>", "event.subscriber.secondary.host" : "<Primary_App_server_IP>",

22. Start Motadata services on Secondary App server as Primary: Start the Motadata services on Secondary App server as Primary.

    sudo service motadata start

23. Ensure Motadata service has started on Secondary App server as Primary: Wait to ensure motadata services has been properly started on Secondary App server as Primary.

    note

    Kindly wait for the motadata-metric-agent-service to spawn before proceeding to next step. sudo watch service motadata status.

24. Stop Motadata service on Secondary App server:

    sudo service motadata stop

25. Revert the Secondary App server installation.mode to Secondary: Change the installation.mode to secondary from Secondary App server.

    note

    Kindly replace the <Primary/Secondary_App_server_IP> placeholder with actual IP address of your App servers. vi /motadata/motadata/config/motadata.json Change the given below entries, "installation.mode" : "SECONDARY", "event.publisher.host" : "<Primary_App_server_IP>", "event.subscriber.host" : "<Primary_App_server_IP>", "event.subscriber.secondary.host" : "<Secondary_App_server_IP>",

26. Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.

    sudo service motadata-observer stop

27. Remove the Events folder at Observer server: You will need to rename the events folder for Observer.

    sudo rm -rf /motadata/motadata/events

28. Remove the ha-config* folders at Secondary App server: You will need to remove the ha-config* folders for Secondary App servers.

    sudo rm -rf /motadata/motadata/events/ha-config*

Post-Upgrade Validation

29. Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.

    sudo service motadata-observer start
30. Start the Motadata service on the Primary App server:

    sudo service motadata start
    Once the server is up and running, navigate to Motadata health monitoring screen and ensure Primary App server is registered.
31. Start the Motadata services on all other servers: You can start Motadata services on all other servers including Primary DB, Secondary App, Secondary DB, and Collectors one by one.

    sudo service motadata start
32. Verify all servers are up and running: Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended.

HA-DR Deployment

Pre-Upgrade Validation

note

Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.

note

Ensure there is no data sync backlog among Primary server, Secondary server, and Collector before proceeding to upgrade. Any data yet to be synced will be lost and cannot be recovered.

note

Ensure all servers are up and running. Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended..

Applying Upgrade Patch

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata Services on select servers: Except Primary App and Observer server, stop Motadata services on all other servers.

   sudo service motadata stop

3. Stop Motadata Services on Primary server: Once Motadata services has been stopped on all other servers, stop the service on the Primary server.

   sudo service motadata stop

4. Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.

   sudo service motadata-observer stop

5. Rename the Events folder at Observer Server: You will need to rename the events folder for Observer Server.

   sudo mv /motadata/motadata/events /motadata/motadata/events_old

6. Remove the ha-config* folders at App servers: You will need to rename the ha-config* folders for all App servers. (Primary App, Secondary App, and Replica App).

   sudo rm -rf /motadata/motadata/events/ha-config*

7. Perform a backup of Configuration files for all App servers: Ensure you create a backup for configuration files on all the App server (Primary App, Secondary App, Replica App).

   sudo cp -r /motadata/motadata/config/ /tmp/ 

8. Remove JSON files from the temporary folder located in the Primary App server:

   sudo rm /tmp/config/*json 

9. Create a tar file in the Primary App server:

   sudo tar -cvf /tmp/config.tar /tmp/config/ 

10. Replicate the Config folder with non-JSON files from Primary App server to other App servers: You will need to copy the config folder containing non-JSON files to all other App servers (Secondary App and Replica App).

    sudo scp -r /tmp/config.tar motadata@<App_server_IP>:/tmp/ 
    note

    Kindly replace the <App_server_IP> placeholder with actual IP address of your App servers.

11. Overwrite the non-JSON files on other App servers: Execute the below-mentioned commands one by one on all other app servers (Secondary App and Replica App server).

    sudo tar -xvf /tmp/config.tar 

    sudo cp /tmp/tmp/config/* /motadata/motadata/config 

12. Perform the Upgrade on all Servers: You can now start upgrading all servers (Observer, Primary App. Primary DB, Secondary App, Secondary DB, Replica App, Replica DB, and Collectors)

• Download AIOPS_UPGRADE.zip: Download and place the AIOPS_UPGRADE.zip file in the /motadata directory on all servers.

• Unzip the Upgrade Patch:

  unzip AIOPS_UPGRADE.zip

• Run the Upgrade Script: After unzipping the patch, run the upgrade script:

  sudo ./aiops-upgrade.sh

Migration Patch on Primary Server

13. Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.

    sudo service motadata-observer start

14. Start Motadata services on Primary server: Once Motadata services has been started on Observer server. Start the Motadata services on Primary App server.

    sudo service motadata start

15. Ensure Motadata service has started on Primary App server: Wait to ensure motadata services has been properly started on Primary App server.

    sudo watch service motadata status
    note

    Kindly wait for the motadata-metric-agent-service to spawn before proceeding to next step.

16. Stop Motadata service on Primary App server:

    sudo service motadata stop

17. Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.

    sudo service motadata-observer stop 

18. Remove the Events folder at Observer server: You will need to rename the events folder for Observer.

    sudo rm -rf /motadata/motadata/events 

19. Remove the ha-config* folders at Primary App server: You will need to remove the ha-config* folders for Primary App servers.

    sudo rm -rf /motadata/motadata/events/ha-config* 

Migration Patch on Secondary Server

20. Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.

    sudo service motadata-observer start 
21. Change the Secondary App server installation.mode to Primary: Change the installation.mode to primary from Secondary App server.
    note

    Kindly replace the <Primary/Secondary_App_server_IP> placeholder with actual IP address of your App servers. vi /motadata/motadata/config/motadata.json Change the given below entries, "installation.mode" : "PRIMARY", "event.publisher.host" : "<Secondary_App_server_IP>", "event.subscriber.host" : "<Secondary_App_server_IP>", "event.subscriber.secondary.host" : "<Primary_App_server_IP>",

22. Start Motadata services on Secondary App server as Primary: Start the Motadata services on Secondary App server as Primary.

    sudo service motadata start
23. Ensure Motadata service has started on Secondary App server as Primary: Wait to ensure motadata services has been properly started on Secondary App server as Primary.
    note

    Kindly wait for the motadata-metric-agent-service to spawn before proceeding to next step. sudo watch service motadata status.

24. Stop Motadata service on Secondary App server:

    sudo service motadata stop
25. Revert the Secondary App server installation.mode to Secondary: Change the installation.mode to secondary from Secondary App server.
    note

    Kindly replace the <Primary/Secondary_App_server_IP> placeholder with actual IP address of your App servers. vi /motadata/motadata/config/motadata.json Change the given below entries, "installation.mode" : "SECONDARY", "event.publisher.host" : "<Primary_App_server_IP>", "event.subscriber.host" : "<Primary_App_server_IP>", "event.subscriber.secondary.host" : "<Secondary_App_server_IP>",

26. Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.

    sudo service motadata-observer stop
27. Remove the Events folder at Observer server: You will need to rename the events folder for Observer.

    sudo rm -rf /motadata/motadata/events
28. Remove the ha-config* folders at Secondary App server: You will need to remove the ha-config* folders for Secondary App servers.

    sudo rm -rf /motadata/motadata/events/ha-config*

Migration Patch on Replica Server

29. Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.

    sudo service motadata-observer start
30. Change the Replica App server installation.mode to Primary: Change the installation.mode to primary from Replica App server.
    note

    Kindly replace the <Failover_App_server_IP> placeholder with actual IP address of your App servers. vi /motadata/motadata/config/motadata.json Change the given below entries, "installation.mode" : "PRIMARY", "event.publisher.host" : "<Failover_App_server_IP>", "event.subscriber.host" : "<Failover_App_server_IP>",

31. Start Motadata services on Replica App server as Primary: Start the Motadata services on Replica App server as Primary.

    sudo service motadata start
32. Ensure Motadata service has started on Replica App server as Primary: Wait to ensure motadata services has been properly started on Replica App server as Primary.
    note

    Kindly wait for the motadata-metric-agent-service to spawn before proceeding to next step. sudo watch service motadata status.

33. Stop Motadata service on Failover App server:

    sudo service motadata stop
34. Revert the Replica App server installation.mode to Failover: Change the installation.mode to Failover from Primary App server.
    note

    Kindly replace the <VIP/Hostname> placeholder with actual IP address/ Hostname of your App servers. vi /motadata/motadata/config/motadata.json Change the given below entries, "installation.mode" : "FAILOVER", "event.publisher.host" : "<VIP/Hostname>", "event.subscriber.host" : "<VIP/Hostname>",

35. Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.

    sudo service motadata-observer stop
36. Remove the Events folder at Observer server: You will need to rename the events folder for Observer.

    sudo rm -rf /motadata/motadata/events
37. Remove the ha-config* folders at Replica App server: You will need to remove the ha-config* folders for Replica App servers.

    sudo rm -rf /motadata/motadata/events/ha-config*

Post-Upgrade Validation

38. Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.

    sudo service motadata-observer start

39. Start the Motadata service on the Primary App server:

    sudo service motadata start

    Once the server is up and running, navigate to Motadata health monitoring screen and ensure Primary App server is registered.

40. Start the Motadata services on all other servers: You can start Motadata services on all other servers including Primary DB, Secondary App, Secondary DB, Replica App, Replica DB, and Collectors one by one.

    sudo service motadata start

41. Verify all servers are up and running: Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended.

Agent Upgrade (Ubuntu, Windows, RHEL/CentOS)

1. Download MOTADATA-MANAGER_UPGRADE.zip: Download the agent file from the above link and Upload the file on the Agent upgrade screen.
2. Run Compatibility Check: Click 'Run Compatibility Check' and then click on 'Upgrade Now' for the agent that need to be upgraded.
3. Wait for few moments: Kindly wait for a few moments for the upgrade to be completed.
4. Download the Agent Upgrade Zip: Download the appropriate agent upgrade zip from the above link corresponding to the OS version of your system.
5. Run Compatibility Check: Click 'Run Compatibility Check' and then click on 'Upgrade Now' for the agent that need to be upgraded.